fix random crashes
Reported by Aurelien Botman | January 26th, 2010 @ 08:20 PM | in 0.6
Sometimes the backend chokes on data which, if ordered differently, generates a perfectly fine graph.
Currently, no reliable cause can be isolated for the crash.
Comments and changes to this ticket
-
Aurelien Botman February 1st, 2010 @ 09:26 PM
- → Milestone changed from “0.5” to “0.5.1”
-
Aurelien Botman February 27th, 2010 @ 07:33 PM
- → Milestone changed from “0.5.1” to “0.5.2”
We could modify the backend to output errors back to the front-end (right now it spits out lots of debug info), this could be done with a "front-end" flag. This will also solve ticket #6.
What we'd do with the output is unclear; probably just display it to the user. Maybe we can spot patterns then in bug reports which would point to a cause for these "random" crashes.
-
Aurelien Botman April 24th, 2010 @ 04:56 PM
- → Milestone changed from “0.5.2” to “0.6”
-
Aurelien Botman August 27th, 2010 @ 07:52 PM
Fixed in 0.5.2: backend gives frontend feedback on errors, which get logged and shown to user.
Fixed in 0.5.4: some crash conditions have been identified and fixed. Not closing bug because unclear if completely resolved. -
Aurelien Botman October 24th, 2010 @ 09:45 PM
- → State changed from “open” to “resolved”
Backtraces indicate no serious crashes with unknown causes occurred in the past two months, so I'm going to go ahead and declare this 'fixed'. Closing ticket.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
This is the bug reporting and support system for tilige.com.
People watching this ticket
Tags
Referenced by
-
#6 Timeout should be added to graph generation
See ticket #7 -- that approach will help with this issue....